feat(schema): Critical Extension Gate + LockedArtifact DAG tracking - #127
Closed
telleroutlook wants to merge 1 commit into
Closed
feat(schema): Critical Extension Gate + LockedArtifact DAG tracking#127telleroutlook wants to merge 1 commit into
telleroutlook wants to merge 1 commit into
Conversation
…m & aep-record Absorbs two proven designs from the ASF (Autonomous Software Factory) protocol spec into wasmagent-protocol, grounded in WasmAgent's provability-first positioning. ## Changes ### agentbom v0.2 - block: CRD-like mechanism where extensions MUST cause consumers to abort if the namespace is unrecognised. Prevents silent security downgrades (e.g. Trust Passport requirements being silently dropped when an older runtime processes the BOM). - items now enforce the namespace pattern (e.g. ), making permission grants machine-parseable and auditable. ### aep-record (aep/v0.3, additive) - : reusable definition requiring + . - array: DAG artifact tracking with nine lifecycle states (pending → completed/failed/cancelled). The conditional enforces LockedArtifact only when state == completed — completed artifacts are always cryptographically pinned, in-progress ones are not constrained. ## Test fixtures added - valid: , - invalid: , , All 18 JS tests and full Python conformance (with jsonschema) pass. Note: jq reformatted the two modified schema files to expanded style; semantics are unchanged. biome 1.9.4 (lineWidth: 100) is not installed on this host.
Contributor
Author
|
This PR adds the Critical Extension Gate and LockedArtifact DAG tracking to agentbom and aep-record schemas. It has merge conflicts with main. Please re-open as a fresh issue to be implemented on top of current main if this feature is still needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Absorbs two proven designs from the ASF (Autonomous Software Factory) protocol spec into wasmagent-protocol, grounded in WasmAgent's provability-first positioning.
agentbom v0.2
Critical Extension Gate (
extensionsblock): CRD-like mechanism wherecritical: trueextensions MUST cause consumers to abort if the namespace is unrecognised. Prevents silent security downgrades — e.g. a Trust Passport requirement being silently dropped when an older runtime processes the BOM.Permission namespace pattern:
permission_layer.granted_scopesitems now enforce^[a-z0-9.-]+:[a-zA-Z0-9.*_/-]+$(e.g.network.egress:registry.npmjs.org), making permission grants machine-parseable and auditable rather than free-form strings.aep-record (additive, aep/v0.3)
LockedArtifact (
$defs/LockedArtifact): reusable definition requiringoutput_hash+output_uri.run_artifactsarray: DAG artifact tracking with nine lifecycle states (pending → completed/failed/cancelled). UsesallOf/if/thenconditional to enforce LockedArtifact only whenstate == completed— in-progress artifacts are unconstrained, completed ones are always cryptographically pinned.Why
The Critical Extension Gate solves a real failure mode: a consumer that does not understand a security-critical extension must not silently succeed. This is the same principle as Kubernetes CRD
x-kubernetes-validations— unknown critical extensions abort, not skip.The LockedArtifact pattern closes the provability gap where an AEP record could claim an artifact was produced without providing any cryptographic evidence. Completed = locked is an invariant, not a suggestion.
Tests